Protocol implementation on the Nectar communication processor Eric

We have built a high-speed local-area network called Nectar that uses programmable communication processors as host interfaces. In contrast to most protocol engines, our communication processors have a flexible runtime system that supports multiple transport protocols as well as application-specific activities. In particular, we have implemented the TCP/IP protocol suite and Nectar-specific communication protocols on the communication processor. The Nectar network current! y has 25 hosts and has been in use for over a year. The flexibility of our communication processor design does not compromise its performance. The latency of a remote procedure call between application tasks executing on two Nectar hosts is less than 500 μsec. The same tasks can obtain a throughput of 28 Mbil/sec using either TCP/IP or Nectar-specific transport protocols. This throughput is limited by the VME bus that connects a host and its communication processor. Application tasks executing on two communication processors can obtain 90 Mbil/sec of the possible 100 Mbil/sec physical bandwidth using Nectar-specific transport protocols. CAtt?~:~r~~::: f·.'i;:J ... :.o:~ t~~,c~v~c~~;~TY P~T\~~1GU~~t,:-.}'-fJ PA 152'iJa3S$,!l DEFS-ALA0010708 INTEL Ex.1022.005